@Gijs Yes! Tested rc11 yesterday and it worked just fine. Thx!

I tried reflashing the wipy but this time I unticked "enable Pybytes/SmartCofig support" and I can see the AP on my PC now [image: 1582739721070-pycommupgrade.png]

@robert-hh Ok, thanks !

Hello, I released a fully new version (v2.0) of my web server here : https://github.com/jczic/MicroWebSrv2. Open source MIT, fully asynchronous, more robust, more fast and more efficient on Pycom modules. It is delivered with a good documentation. For captive portal, you can use a simple DNS server here (see readme) : https://github.com/jczic/MicroDNSSrv Thank you for your support and feedback. ☺️

@mfalkvidd, @Paul-Thornton thank you for taking care of this! I am looking forward to a solution as soon as possible. Not only my project strongly depends on this function as it is a rather basic functionality. At least, I could not find any alternative way of detecting connected devices in AP mode.

Do the connected clients also return false or is it just the node setup as an AP

@jcaron Thank you very much for your reply. Turning off WiFi on boot seems to fix the issue. Apparently it was related to the PyCom starting in AP mode for telnet.

@dan, how did you fix this problem? Would you please post the code on both devices that you used? I am running in to the same issue. Thanks

@livius Thanks a lot. Now both of my LoPy works in AP mode. com port issue is adressed and fix will be released in next firmware @daniel can say when. I hope it is very soon.

Dear @Roqueton, we have tried to implement SIM800 PPPoS support (WIP), see also [1,2,3]. With kind regards, Andreas. [1] https://github.com/pycom/pycom-micropython-sigfox/pull/408 [2] https://community.hiveeyes.org/t/ppp-over-serial-pppos-support-for-micropython-on-esp32/2994 [3] https://community.hiveeyes.org/t/unlocking-and-improving-the-pythings-sim800-gprs-module-for-micropython/2978/29